NTISthis.com

Evidence Guide: ICTPRG509 - Build using rapid application development

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG509 - Build using rapid application development

What evidence can you provide to prove your understanding of each of the following citeria?

Construct an application using RAD

  1. Capture and record business rules, using a methodology well-suited for the chosen RAD and RAD techniques
  2. Design an application with a focus on modularity and future extension
  3. Develop the code by other RAD tools
  4. Build and demonstrate the completed transaction to the user, for revision within the agreed terms of reference
  5. Take action to ensure that the design caters for continuous change, by involving the user in the iteration process
  6. Provide quality assurance (QA) testing throughout the phase and provide feedback to the appropriate person
  7. Use code optimisers and performance tools
Capture and record business rules, using a methodology well-suited for the chosen RAD and RAD techniques

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design an application with a focus on modularity and future extension

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop the code by other RAD tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Build and demonstrate the completed transaction to the user, for revision within the agreed terms of reference

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Take action to ensure that the design caters for continuous change, by involving the user in the iteration process

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Provide quality assurance (QA) testing throughout the phase and provide feedback to the appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Use code optimisers and performance tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare the handover stage

  1. Track the implemented modules, and follow up where necessary with the appropriate person
  2. Review user and builds for each module in the deliverables as preparation for handover
  3. Compare the specification and implementation schedules for each module, and confirm the functional requirements, according to the specifications
  4. Document the completed work
Track the implemented modules, and follow up where necessary with the appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review user and builds for each module in the deliverables as preparation for handover

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare the specification and implementation schedules for each module, and confirm the functional requirements, according to the specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the completed work

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Construct an application using RAD

1.1 Capture and record business rules, using a methodology well-suited for the chosen RAD and RAD techniques

1.2 Design an application with a focus on modularity and future extension

1.3 Develop the code by other RAD tools

1.4 Build and demonstrate the completed transaction to the user, for revision within the agreed terms of reference

1.5 Take action to ensure that the design caters for continuous change, by involving the user in the iteration process

1.6 Provide quality assurance (QA) testing throughout the phase and provide feedback to the appropriate person

1.7 Use code optimisers and performance tools

2. Prepare the handover stage

2.1 Track the implemented modules, and follow up where necessary with the appropriate person

2.2 Review user and builds for each module in the deliverables as preparation for handover

2.3 Compare the specification and implementation schedules for each module, and confirm the functional requirements, according to the specifications

2.4 Document the completed work

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Construct an application using RAD

1.1 Capture and record business rules, using a methodology well-suited for the chosen RAD and RAD techniques

1.2 Design an application with a focus on modularity and future extension

1.3 Develop the code by other RAD tools

1.4 Build and demonstrate the completed transaction to the user, for revision within the agreed terms of reference

1.5 Take action to ensure that the design caters for continuous change, by involving the user in the iteration process

1.6 Provide quality assurance (QA) testing throughout the phase and provide feedback to the appropriate person

1.7 Use code optimisers and performance tools

2. Prepare the handover stage

2.1 Track the implemented modules, and follow up where necessary with the appropriate person

2.2 Review user and builds for each module in the deliverables as preparation for handover

2.3 Compare the specification and implementation schedules for each module, and confirm the functional requirements, according to the specifications

2.4 Document the completed work

Evidence of the ability to:

design an application and develop high quality code, according to client specifications

provide quality assurance testing and monitoring

effectively demonstrate use of code optimisers using rapid application development (RAD) techniques

accurately document completed work.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

outline industry-accepted prototyping tools

describe quality assurance practices as they relate to RAD

describe the impact that the client business domain will have on RAD in particular there effect on:

cost

quality

outline the role of the stakeholder, and the involvement required in RAD

describe three or more current industry development methodologies

identify and apply three or more programming languages

identify and apply the most appropriate RAD tool, taking into consideration the targeted platform or multi-platform options.